Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How SeBS could be used with Fission? #69

Closed
YasminBZ opened this issue Jan 8, 2021 · 6 comments
Closed

How SeBS could be used with Fission? #69

YasminBZ opened this issue Jan 8, 2021 · 6 comments
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@YasminBZ
Copy link

YasminBZ commented Jan 8, 2021

Hello,

I would like to know how to use SeBS with Fission please.

I appreciate your help.

Thank you.

@mcopik
Copy link
Collaborator

mcopik commented Jan 19, 2021

@YasminBZ Thanks for your interest in SeBS! We're working on the support for open-source platforms, it is planned for next releases.

There's a branch with support for Fission partially implemented: https://github.com/spcl/serverless-benchmarks/tree/feature_fission

@mcopik mcopik added enhancement New feature or request good first issue Good for newcomers labels Feb 16, 2023
@mcopik
Copy link
Collaborator

mcopik commented Feb 16, 2023

We have ongoing progress toward running SeBS benchmarks on Fission. A good first step would be clean the branch and update it to the current interface.

@Stazz0
Copy link

Stazz0 commented Mar 1, 2024

Hii @mcopik , I'm encountering a number of errors during the feature_fission branch update. It seems to be related to whitespace issues and merge conflicts in .gitignore, sebs.py, s3.py. Could you advise me on the best way to resolve these – keeping both changes, or choosing one? Thanks in advance!
Screenshot from 2024-02-28 00-14-31

@mcopik
Copy link
Collaborator

mcopik commented Mar 6, 2024

@Stazz0 Hi! Thanks for your interest in the project and apologies for the slow reply.

Since this branch is quite old, I'm afraid I will have to take a look into this - we've had many breaking changes over the years. I will try to update the branch as soon as possible.

@mcopik
Copy link
Collaborator

mcopik commented Mar 9, 2024

@Stazz0 The branch should be up-to-date with the master. Please merge instead of rebasing on this branch, as it was created a long time ago and we had many conflicts resolved over that time.

@mcopik
Copy link
Collaborator

mcopik commented Jul 26, 2024

Closing this issue in favor of #61 - @prajinkhadka is working on this currently.

@mcopik mcopik closed this as completed Jul 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

3 participants