Skip to content

Actions: Lightning-AI/pytorch-lightning

Actions

All workflows

Actions

Loading...
Loading

Showing runs from all workflows
3,186 workflow run results
3,186 workflow run results

Filter by Event

Filter by Status

Filter by Branch

Filter by Actor

Error: Invalid value for '--accelerator': 'auto' is not one of 'cpu', 'gpu', 'cuda', 'mps', 'tpu'. Probot #29500: Issue #20451 labeled by lantiga
23s
23s
Error: Invalid value for '--accelerator': 'auto' is not one of 'cpu', 'gpu', 'cuda', 'mps', 'tpu'. Probot #29498: Issue #20451 labeled by lantiga
23s
23s
Error: Invalid value for '--accelerator': 'auto' is not one of 'cpu', 'gpu', 'cuda', 'mps', 'tpu'. Probot #29499: Issue #20451 labeled by lantiga
23s
23s
Add str method to datamodule Label Pull Requests #9616: Pull request #20301 synchronize by MrWhatZitToYaa
11s
11s
Enforce port range for Apps on localhost (similar to cloudspace) Label Issues #2661: Issue #20470 opened by hummuscience
12s
12s
Enforce port range for Apps on localhost (similar to cloudspace) Probot #29497: Issue #20470 labeled by hummuscience
22s
22s
Enforce port range for Apps on localhost (similar to cloudspace) Probot #29496: Issue #20470 labeled by hummuscience
22s
22s
[BUG] (DataLoader) sanity check fails due to Input type (torch.FloatTensor) and weight type (torch.cuda.FloatTensor) Probot #29495: Issue #20456 labeled by lantiga
55s
55s
Make sure the upcoming change in the default for weights_only from False to True is handled correctly Probot #29494: Issue #20450 labeled by lantiga
26s
26s
Jax Support within Lightning Probot #29493: Issue #20458 labeled by lantiga
23s
23s
A gracefull design to introduce third-party models as tool for validation Probot #29492: Issue #20464 labeled by lantiga
23s
23s
Allowing setting timeout in DeepSpeedStrategy Probot #29491: Issue #20466 labeled by lantiga
22s
22s
Allowing setting timeout in DeepSpeedStrategy Probot #29490: Issue #20466 labeled by lantiga
24s
24s
Trainer with logger=False still produces logs Probot #29489: Issue #20467 labeled by lantiga
21s
21s
Why 'val_check_interval' should be more steps then that of a epoch when set as integer? Probot #29488: Issue #20468 labeled by lantiga
23s
23s
Pickling error when using cuda in collate_fn Probot #29487: Issue #20469 labeled by lantiga
23s
23s
Pickling error when using cuda in collate_fn Probot #29486: Issue #20469 labeled by Richienb
21s
21s
Pickling error when using cuda in collate_fn Probot #29485: Issue #20469 labeled by Richienb
22s
22s
Pickling error when using cuda in collate_fn Label Issues #2660: Issue #20469 opened by Richienb
16s
16s
Why 'val_check_interval' should be more steps then that of a epoch when set as integer? Label Issues #2659: Issue #20468 opened by JohnHerry
12s
12s
Why 'val_check_interval' should be more steps then that of a epoch when set as integer? Probot #29484: Issue #20468 labeled by JohnHerry
21s
21s
Why 'val_check_interval' should be more steps then that of a epoch when set as integer? Probot #29483: Issue #20468 labeled by JohnHerry
23s
23s
Test PyTorch Test PyTorch #14371: Scheduled
25m 25s master
master
25m 25s
Docker builds Docker builds #2275: Scheduled
11m 0s master
master
11m 0s
Test Fabric Test Fabric #9737: Scheduled
12m 52s master
master
12m 52s