Use correct ordering semantics for narrowing upper-bounded Python requirements #14352
Job | Run time |
---|---|
29s | |
41s | |
10s | |
24s | |
11s | |
5s | |
1m 20s | |
3m 58s | |
1m 34s | |
52s | |
5m 12s | |
1m 23s | |
5m 33s | |
1m 5s | |
5m 16s | |
37s | |
5m 3s | |
34s | |
9m 0s | |
1m 3s | |
1m 50s | |
1m 56s | |
12s | |
16s | |
18s | |
26s | |
1m 19s | |
18s | |
1m 2s | |
24s | |
11s | |
54s | |
48s | |
21s | |
29s | |
24s | |
33s | |
1m 43s | |
34s | |
4m 15s | |
31s | |
34s | |
15s | |
23s | |
31s | |
1m 21s | |
1m 29s | |
39s | |
1m 18s | |
49s | |
42s | |
24s | |
44s | |
1m 44s | |
2m 1s | |
40s | |
1m 0s | |
1h 17m 48s |