Skip to content

get-pip.py no longer works on rustpython.  #3097

Closed

Description

@andrew-ld
andrew@arch ~/RustPython (main)> wget https://bootstrap.pypa.io/get-pip.py
2021-09-20 20:35:20 (6.41 MB/s) - ‘get-pip.py.1’ saved [1957374/1957374]

andrew@arch ~/RustPython (main)> cargo run --release --features=ssl get-pip.py 
    Finished release [optimized] target(s) in 0.11s
     Running `target/release/rustpython get-pip.py`

^C^C^C^C

something seems to be going deadlock.

syscall trace: https://gist.github.com/andrew-ld/86f44239802a414bf00f0f42b601c677

RustPython commit: e6e2204
Rust version: 1.55.0 (c8dfcfe04 2021-09-06)
Os: archlinux with linux 5.14

Activity

  1. DimitrisJim commented on Sep 27, 2021

    @DimitrisJim
    Member

    bump, can you try running this again? I could repro when I first saw it but currently cannot.

  2. coolreader18 commented on Sep 27, 2021

    @coolreader18
    Member

    This currently works on my machine as well, there are just some warnings which I fixed in #3158

  3. andrew-ld commented on Sep 30, 2021

    @andrew-ld
    Author

    This currently works on my machine

  4. andrew-ld commented on Oct 2, 2021

    @andrew-ld
    Author

    seems to be broken again
    commit: 6b1af9a

    andrew@arch ~/RustPython (main)> cargo run --release --all-features get-pip.py
        Finished release [optimized] target(s) in 0.12s
         Running `target/release/rustpython get-pip.py`
    fish: Job 1, 'cargo run --release --all-featu…' terminated by signal SIGKILL (Forced quit)
    
    
  5. oroppas commented on Oct 12, 2021

    @oroppas

    Works on my Arch Linux.

  6. andrew-ld commented on Oct 13, 2021

    @andrew-ld
    Author

    from me it keeps using so much ram until it has a sigkill

  7. oroppas commented on Oct 13, 2021

    @oroppas

    Ah, I see. cargo run --release --features ssl get-pip.py should work on Arch Linux.
    What @andrew-ld is trying now cargo run --release --all-features get-pip.py doesn't work
    as it hogging all available memory.

    We should be able to isolate which feature causes the issue by adding feature one by one.

  8. oroppas commented on Oct 13, 2021

    @oroppas

    cargo run --release --features "ssl, flame-it" get-pip.py causes memory allocation failure.

  9. DimitrisJim commented on Oct 14, 2021

    @DimitrisJim
    Member

    I think that's just too much profiling information getting collected. Running it with other scripts (i.e try running the tests for itertools) should also lead to monstrous RAM consumption.

  10. DimitrisJim commented on Oct 15, 2021

    @DimitrisJim
    Member

    @andrew-ld could you check if the hanging is present? flame-it chewing up all the ram is something that I don't think will be fixed, it has its usages with scripts that don't do as much as get-pip does.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions