Push gitlab and cannot find issue

[baegseungheon]

Hello,

I am contacting you because I am experiencing an issue with a push command. I executed $ git push origin submission-v2.0 and received the following output:

Uploading LFS objects: 100% (10/10), 5.9 GB | 0 B/s, done.
Enumerating objects: 1, done.
Counting objects: 100% (1/1), done.
Writing objects: 100% (1/1), 170 bytes | 170.00 KiB/s, done.
Total 1 (delta 0), reused 0 (delta 0), pack-reused 0 (from 0)
remote:
          #///(            )///#
         ////      ///      ////
        /////   //////////   ////
        /////////////////////////
     /// /////////////////////// ///
   ///////////////////////////////////
  /////////////////////////////////////
    )////////////////////////////////(
     /////                      /////
   (///////   ///       ///    //////)
  ///////////    ///////     //////////
(///////////////////////////////////////)
          /////           /////
            /////////////////
               ///////////
To gitlab.aicrowd.com:baegseungheon/amazon-kdd-cup-2024-starter-kit.git
* [new tag]         submission-v2.0 -> submission-v2.0

I confirmed that the push was successful and the tag submission-v2.0 can be seen in my repository. However, I have not received any issue notifications. What could be the problem?

[gluver]

Hi, @yilun_jin,Was the submission dealine ended earlier We are having the same issue, somehow all new submissions didn’t tigger the benchmarking pipeline. Thought the deadline is 23:55 UTC time as displayed on the camp webpages

.

[baegseungheon]

There are only a few hours left, and this error is too critical.

[gaozhanfire]

Have you solved the same problem?

[gaozhanfire]

@yilun_jin This seems like a bug on the AIcrowd platform. After today’s deadline, could the platform provide some additional time for teams that were unable to submit successfully?

[fersebasIn]

Same issue here , submissions are not working for my team

[yilun_jin]

@baegseungheon @gluver @gaozhanfire @fersebasIn Phase 1 is re-started until May 19th, 12:00 UTC. Let us know if the same error persists.

[fersebasIn]

Finally it worked after trying yesterday several times. Thanks @yilun_jin for give us more time

[yuezzz]

sovled,thanks!